Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Honor REQUESTS_CA_BUNDLE env var #586

Merged
merged 3 commits into from
Jan 9, 2014
Merged

Conversation

jamesls
Copy link
Member

@jamesls jamesls commented Jan 9, 2014

This allows a user to specify a different cert bundle via an
env var. This uses the new verify arg added to get_endpoint
in botocore.

Previously it was creating an Endpoint object and then setting the
verify attribute, but the REQUESTS_CA_BUNDLE lookup happens before
an Endpoint object is created, so we would override the value
from the env var. By using the verify arg in get_endpoint we
can avoid this.

Note that this depends on boto/botocore#203 and will
fail the tests until this is merged in.

This allows a user to specify a different cert bundle via an
env var.  This uses the new verify arg added to get_endpoint
in botocore.

Previously it was creating an Endpoint object and then setting the
verify attribute, but the REQUESTS_CA_BUNDLE lookup happens before
an Endpoint object is created, so we would override the value
from the env var.  By using the verify arg in get_endpoint we
can avoid this.
@jamesls
Copy link
Member Author

jamesls commented Jan 9, 2014

Ok, the PR should pass now that the PR from botocore is merged in.

However, given we're now in the aws cli territory, should this just be called AWS_CA_BUNDLE, and we could possibly do the env var lookup here and explicitly pass a value to botocore?

I can see why botocore would honor this value, but perhaps in the CLI we need something more specific.

@garnaat
Copy link
Contributor

garnaat commented Jan 9, 2014

I would favor using AWS_CA_BUNDLE. I think that will make more sense in customer-facing documentation explaining this.

@jamesls
Copy link
Member Author

jamesls commented Jan 9, 2014

Ok, I'll update this PR to do an env var lookup for AWS_CA_BUNDLE.

@jamesls
Copy link
Member Author

jamesls commented Jan 9, 2014

Ok, code updated to check for, and use, AWS_CA_BUNDLE.

@garnaat
Copy link
Contributor

garnaat commented Jan 9, 2014

LGTM

@jamesls jamesls merged commit f2db71d into aws:develop Jan 9, 2014
@jamesls jamesls deleted the cacert-envar branch June 23, 2014 18:27
thoward-godaddy pushed a commit to thoward-godaddy/aws-cli that referenced this pull request Feb 12, 2022
thoward-godaddy pushed a commit to thoward-godaddy/aws-cli that referenced this pull request Feb 12, 2022
* fix: Functional tests must run on localhost to work in Windows (aws#552)

* fix: spacing typo in Log statement in start-lambda (aws#559)

* docs: Fix syntax highlighting in README.md (aws#561)

* docs: Change jest to mocha in Nodejs init README (aws#564)

* docs: Fix @mhart link in README (aws#562)

* docs(README): removed cloudtrail, added SNS to generate-event (aws#569)

* docs: Update repo name references (aws#577)

* feat(debugging): Fixing issues around debugging Golang functions. (aws#565)

* fix(init): Improve current init samples around docs and fixes (aws#558)

* docs(README): Update launch config to SAM CLI from SAM Local (aws#587)

* docs(README): Update sample code for calling Local Lambda Invoke (aws#584)

* refactor(init): renamed handler for camel case, moved callback call up (aws#586)

* chore: aws-lambda-java-core 1.1.0 -> 1.2.0 for java sam init (aws#578)

* feat(validate): Add profile and region options (aws#582)

Currently, `sam validate` requires AWS Creds (due to the SAM Translator).
This commits adds the ability to pass in the credientials through a profile
that is configured through `aws configure`.

* docs(README): Update README prerequisites to include awscli (aws#596)

* fix(start-lambda): Remove Content-Type Header check (aws#594)

* docs: Disambiguation "Amazon Kinesis" (aws#599)

* docs: Adding instructions for how to add pyenv to your PATH for Windows (aws#600)

* docs: Update README with small grammar fix (aws#601)

* fix: Update link in NodeJS package.json (aws#603)

* docs: Creating instructions for Windows users to install sam (aws#605)

* docs: Adding a note directing Windows users to use pipenv (aws#606)

* fix: Fix stringifying λ environment variables when using Python2 (aws#579)

* feat(generate-event): Added support for 50+ events (aws#612)

* feat(invoke): Add region parameter to all invoke related commands (aws#608)

* docs: Breaking up README into separate files to make it easier to read (aws#607)

* chore: Update JVM size params to match docker-lambda (aws#615)

* feat(invoke): Invoke Function Without Parameters through --no-event (aws#604)

* docs: Update advanced_usage.rst with clarification on --env-vars usage (aws#610)

* docs: Remove an extra word in the sam packaging command (aws#618)

* UX: Improves event names to reflect Lambda Event Sources (aws#619)

* docs: Fix git clone typo in installation docs (aws#630)

* docs(README): Callout go1.x runtime support (aws#631)

* docs(installation): Update sam --version command (aws#634)

* chore(0.6.0): SAM CLI Version bump (aws#635)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants